Fix output for divide-x tw class #93
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey @green-coder,
Thank you so much for Girouette!
I've started using the library recently, and noticed that using
divide-xclass seems to produce swapped left/right border rules as compared to Tailwind.In this MR,
:divide-widthwas updated in line with Tailwind's implementationdivide-*classes were added to the example appNB: The update to the example app also revealed that
divide-x-reverserule still might not function as expected - it seems that the rule order in the example app's generated css output causes thedivide-x-10rule to override the redefinition of--gi-divide-x-reversevariable as it does in Tailwind.I couldn't find a way to affect the sorting of garden-fn's results, so decided to create an MR as is with a fix for
divide-xonly.